Thread: get rid of warning: the use of `tmpnam' is dangerous, better use `mkstemp'

Use safe functions at the expensive of almost anything else.

How are you intending to handle the possibility that between creating the name and using the name, that something else won't come along and use the same name?

That is what mkstemp is designed to avoid, those kinds of race conditions.

Besides, if you really need to know it's name, then perhaps mkstemp (and even tmpnam) is the wrong thing to be using. Perhaps roll your own unique name, and add in the current process ID. That stands a fair chance of being unique.

If I understand correctly, the poster probably wants an fstream for the temp file, which poses an interesting problem indeed.

Secure versions are easy to get rid of if others want to compile your code with simple pseudo functions or defines, but it's not easy the other way around, so by all means - go for the safe functions!